HM Telnet Service is an auxiliary application for HostMonitor. It is included into Advanced Host Monitor package. Enterprise license for Advanced Host Monitor already includes a license for HM Telnet Service. Holders of a Lite, Standard or Professional licenses may buy an additional license for Telnet Service separately.

Intro    Settings    Quick start    Commands    System Requirements    Price

This application works like Telnet server and allows you to control HostMonitor remotely using any telnet client. Telnet Service allows you to check brief or detailed status of any test and folder. Also you can disable and enable tests, reset statistics, force tests to execution and even change some parameters of the tests. HM Telnet Service allows you to start or stop monitoring process, enable or disable alerts, change global macro variables, etc.

Features:

• All data transmission between HostMonitor and Telnet Service is encrypted and password protected;
• HostMonitor & Telnet Service allow you to setup different user accounts with different sets of permissions;
• Application can be installed on the HostMonitor's system or can be located on any another system that is accessible by TCP/IP protocol;
• Telnet Service can be started as a regular application or as a Win32 service.

Settings
It is very easy to configure Telnet Service:

RCI (Remote Control Interface) settings

• Address: here you should provide an address of the system where HostMonitor is installed (keep the default '127.0.0.1' if HostMonitor and Telnet Service are installed on the same system)
• Port: please provide TCP port that is used by HostMonitor's Remote Control Interface (1054 by default)
• Timeout: the maximum amount of time (in seconds) that Telnet Service will keep waiting for the reply from HostMonitor before returning an error response to the client.

• Port: TCP port which Telnet Service utilizes to listen for incoming connections from the telnet client (default TCP port for telnet protocol is 23. You may need to change it in case you already have a regular telnet server running on the same system).
  

• Application status: set "Active" to activate Telnet service (it will then start listening for incoming connections and will respond to requests from any telnet client). If you start the software as a Win32 service then telnet server will be activated regardless of this option at the system startup.

• Install / Uninstall: this button allows you to install/uninstall software as a Win32 service
  
• Start / Stop: this button allows you to start/stop the service
  
  

• start HostMonitor

• configure HostMonitor's Remote Control Interface on RCI page in the Options dialog

• setup user accounts: use HostMonitor's menu "User"->"Operators"

• start the Telnet Service. You can start it on the same system where HostMonitor is running or on any system that has TCP/IP connection with HostMonitor's system. E.g. HostMonitor can be installed on the server inside of a corporate network but Telnet Service can be running on your home computer.

• configure Telnet Service: provide an address of the HostMonitor's system and TCP port that you had specified for RCI

That's it. Now you can start telnet client (e.g. standard client included in Windows) and connect to HostMonitor using an address of the system where Telnet Service is running (e.g. 209.173.80.15 or www.mycompany.com).
If you are running regular telnet server and our Telnet Service is installed on the same system, change the TCP port of our Telnet Service from 23 (default) to any other. In this case you will need to specify this port number for telnet client as well.

Commands

When you start telnet client and establish a connection with Telnet Service, you will be asked for your user name and password. You will then get the rights and permissions that are specified in your user account. E.g. "Admin" can perform any operations, "Guest" can only view test statuses, etc.

After logging in you may type commands that Telnet Service will execute. You will then see responses from HostMonitor.
Here are some common rules for the commands:

Examples:
  DisableTest  _AllTCP -r    
  EnableTest   _AllPing      
  RefreshTest  _AllURL       
  RefreshTest  "my router"   
  EnableAll